Skip to content

fix: multiple container tag issue fix #1552

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Dec 9, 2024
Merged

fix: multiple container tag issue fix #1552

merged 3 commits into from
Dec 9, 2024

Conversation

AjitPadhi-Microsoft
Copy link
Contributor

Purpose

  • A fix for multiple container tag issue. Now the image will push to registry based on branch.

Does this introduce a breaking change?

  • Yes
  • No

How to Test

  • Get the code
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install
  • Test the code

What to Check

Verify that the following are valid

  • ...

Other Information

Copy link

github-actions bot commented Dec 6, 2024

Coverage

Coverage Report •
FileStmtsMissCoverMissing
TOTAL310991570% 
report-only-changed-files is enabled. No files were changed during this commit :)

Tests Skipped Failures Errors Time
301 0 💤 0 ❌ 0 🔥 49.213s ⏱️

@Roopan-Microsoft Roopan-Microsoft merged commit 02d0056 into dev Dec 9, 2024
8 of 9 checks passed
Copy link

🎉 This PR is included in version 1.13.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Copy link

github-actions bot commented Jan 3, 2025

🎉 This PR is included in version 1.14.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants